AI SDK Kotlin/ai.torad.aisdk/ToolLoopAgentState

ToolLoopAgentState

data class ToolLoopAgentState(val messages: List<ModelMessage> = emptyList(), val streamingAssistantText: String = "", val currentToolCalls: List<ContentPart.ToolCall> = emptyList(), val pendingApprovals: List<PendingApproval> = emptyList(), val isStreaming: Boolean = false, val isModelLoading: Boolean = false, val error: String? = null, val totalSteps: Int = 0, val lastFinishReason: FinishReason? = null)

Engine-shape state for ToolLoopAgent.

The Vercel AI SDK's Agent interface is stateless per-call — the host passes messages, gets back GenerateResult, manages history itself. For an Android app using a long-lived @AppScope agent (no HTTP boundary, no per-request lifecycle), it's cleaner to treat the agent as a state-holder engine: the agent owns the message log, exposes ToolLoopAgent.engineState as a StateFlow, and the host drives it via ToolLoopAgent.dispatchEngineAction — the same pattern a Compose ViewModel uses for UI state.

The per-call Agent.generate / Agent.stream surface stays available (used by tests and any host that does want stateless calls). The engine surface is layered on top, not a replacement.

Constructors

ToolLoopAgentState

constructor(messages: List<ModelMessage> = emptyList(), streamingAssistantText: String = "", currentToolCalls: List<ContentPart.ToolCall> = emptyList(), pendingApprovals: List<PendingApproval> = emptyList(), isStreaming: Boolean = false, isModelLoading: Boolean = false, error: String? = null, totalSteps: Int = 0, lastFinishReason: FinishReason? = null)